Hi, We have problem for receiving emails attachments with .txt files, and in all .txt attachments in end of the line “=” character is added. Example of .txt attachment. Test Test Test = (“=” character is added) I have noticed this problem due to “Content-Transfer-Encoding quoted-printable” http://techhelp.santovec.us/decode.htm ============================================== Content-Type: text/plain; name="test.txt" Content-Disposition: attachment; filename="test.txt" Content-Transfer-Encoding: quoted-printable ============================================== We are using Exchange server 2003 with SP2. May I know how this can be resolve. Sender side they are using Lotus Notes. Thanks

Not sure what you can do from Excange side, but can't you ask other end to change the encoding to something else other than quoted-printable?Sukh

Hi, The same e-mail received by other Organization doesn’t have this problem. is there any option to control in exchange server 2003 server (receiving end) to decode this.

As far as I know you can do with the sending, not sure about the receiving.Sukh

On Sun, 22 Jan 2012 02:47:58 +0000, rvsmuthu wrote: >The same e-mail received by other Organization doesn?t have this problem. > >is there any option to control in exchange server 2003 server (receiving end) to decode this. Why not use software that understands how to deal correctly with MIME? I'm guessing you're reading the message body without regard to its encoding scheme. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Hi Rich, Can you please explain more about the software that deal correctly with MIME for exchange 2003. My problem is for receiving emails attachments with .txt files, and in all .txt attachments in end of the line “=” character is added. Example of .txt attachment. Test Test Test = (“=” character is added) I have noticed this problem due to “Content-Transfer-Encoding quoted-printable” Thanks

On Sun, 22 Jan 2012 04:35:06 +0000, rvsmuthu wrote: >Can you please explain more about the software that deal correctly with MIME for exchange 2003. MIME is a set of RFCs that define how content can be encoded for transmission. Exchange 2003 usually isn't the problem, the client software is. >My problem is for receiving emails attachments with .txt files, and in all .txt attachments in end of the line ?=? character is added. > > > >Example of .txt attachment. > >Test > >Test > >Test = (?=? character is added) > > > >I have noticed this problem due to ?Content-Transfer-Encoding quoted-printable? Whatever software you're using to read the message isn't handling the encoding properly. Either that or you have some Anti-Virus or Anti-Spam filter that's not reconstructing the message and its attachment correctly. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Hello, Does this issue occur when receiving the emails with .txt attachment properly from an internal user? Check if you have any firewall or mail-scan software on the Exchange Server. Thanks, Simon Wu Exchange Forum Support Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

Hi Simon, No issue for internal mails attachements. The issue is only from external domain which is send by Lotus Notes. Sender side confimed they are using "Content-Transfer-Encoding-Base -64 " for all attchments but when we received its show as "Content-Transfer-Encoding-quoted-printable". Do we need to check anything from exchange server 2003 side. we are using Mcafee GroupShiled for mail scanning. ================================================== --=_mixed 002A23C54825798A_= Content-Type: text/plain; name="test.txt" Content-Disposition: attachment; filename="test.txt" Content-Transfer-Encoding: quoted-printable ==================================================

To make sure what encoding method sender is using enable arhivesink and capture a precat copy of the problem message How to install and use the Archive Sink utility in Exchange Server 2003 http://support.microsoft.com/kb/871110 Also open the pre cat copy of problem eml message from d:\ArchiveSink\Smtp Messages in notepad and paste the entire message on the thread.

Hello, Is there any update on this issue? Thanks, Simon Wu Exchange Forum Support Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

Dear Simon, Thanks for your reply. I have tested .txt attachment between notes servers to diferent exchange 2003 domain servers mailbox but got same results. It seems exchange 2003 couldn’t handle quoted-printable encoding formats. You can refer following link. ====================================================================================================  http://techhelp.santovec.us/decode.htm If the recipient's mail or news program can't handle quoted-printable (many older ones can't), the message will look peculiar with all the equal signs and hexadecimal encoding, but it is still largely readable. ====================================================================================================

In mixed mode, Exchange Server 2003 encodes as quoted-printable or 7-bit (TNEF format) when sending between two servers/recipients in different routing groups and to the Internet. If it can send, not sure why it can't receive. - http://support.microsoft.com/kb/836555Sukh

Hi Sukh, I have already seen this KB. it seems problem with exchange 2003 side.

Hi, did this get resolved? How? Thanks